Expand Azure Functions smoke tests to cover source generator scenarios #604

Copilot · 2026-01-02T22:32:05Z

The smoke test CI lacked end-to-end coverage of Durable Functions source generator outputs, leaving activity/entity/event/sub-orchestration paths unvalidated.

Source generator scenario app: Added SourceGeneratorScenarios.cs with a generated orchestration, activity, entity, durable event, and child orchestration to exercise all generator outputs.
Namespace alignment: Overrode the smoke test project namespace/assembly to AzureFunctionsSmokeTests so generated types resolve correctly.
Smoke runner enhancements: Extended run-smoketests.ps1 to trigger and validate the new generated orchestration outputs alongside the existing HelloCities flow, including null-safe validation and awaited entity updates for deterministic results.
Docs: Updated README structure and flow description to include the generator scenario.

Summary

What changed?

Added source-generator-based orchestration/activity/entity/event coverage and validation.
Updated project namespace settings for generated types.
Enhanced smoke test runner validations to be null-safe and to await entity operations for reliable state checks.
Documented the new scenario.

Why is this change needed?

Ensure end-to-end CI coverage for Durable Task source generator functionality in Azure Functions.

Issues / work items

Resolves #
Related #

Project checklist

Release notes are not required for the next release
- Otherwise: Notes added to release_notes.md
Backport is not required
- Otherwise: Backport tracked by issue/PR #issue_or_pr
All required tests have been added/updated (unit tests, E2E tests)
Breaking change?
- If yes:
  - Impact:
  - Migration guidance:

AI-assisted code disclosure (required)

Was an AI tool used? (select one)

No
Yes, AI helped write parts of this PR (e.g., GitHub Copilot)
Yes, an AI agent generated most of this PR

If AI was used:

Tool(s): GitHub Copilot Coding Agent
AI-assisted areas/files: AzureFunctionsSmokeTests orchestration/activity/entity/event code, smoke runner script, PR description
What you changed after AI output: Adjusted validation logic to be null-safe; switched entity increment to CallEntityAsync; finalized PR metadata

AI verification (required if AI was used):

I understand the code and can explain it
I verified referenced APIs/types exist and are correct
I reviewed edge cases/failure paths (timeouts, retries, cancellation, exceptions)
I reviewed concurrency/async behavior
I checked for unintended breaking or behavior changes

Testing

Automated tests

Result: dotnet build test/AzureFunctionsSmokeTests/AzureFunctionsSmokeTests.csproj

Manual validation (only if runtime/behavior changed)

Environment (OS, .NET version, components): Ubuntu-latest, .NET 8, Docker
Steps + observed results:
1. (Not rerun after latest change) Prior docker smoke run: HelloCities and generated orchestration completed successfully
Evidence (optional): N/A

Notes for reviewers

N/A

Original prompt

update smoke test ci to expand to test all source generator functionalities for durable function case work as expected comprehensively

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: YunchuWang <[email protected]>

Copilot

Pull request overview

This PR enhances the Azure Functions smoke tests to provide comprehensive end-to-end validation of the Durable Task source generator functionality. Previously, the smoke tests only validated basic orchestration scenarios without exercising the source generator's outputs for activities, entities, events, and sub-orchestrations.

Key changes:

Added comprehensive source generator scenario testing with class-based orchestrators, activities, entities, and durable events
Extended PowerShell test runner to validate all generated extension methods and their interactions
Configured project namespace properties to ensure generated types resolve correctly

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs	New file containing GeneratedOrchestration that exercises all source generator outputs: class-based activities (ComposeGreeting, CountCharactersActivity), entity operations (GeneratorCounter), durable events (GeneratorSignal), and child orchestrations
test/AzureFunctionsSmokeTests/run-smoketests.ps1	Extended with Steps 9-10 to trigger and validate the source generator orchestration, including assertions for greeting text, entity counter values, child orchestration responses, and event message handling
test/AzureFunctionsSmokeTests/AzureFunctionsSmokeTests.csproj	Added TopLevelNamespace, RootNamespace, and AssemblyName properties to align namespace resolution for source-generated extension methods
test/AzureFunctionsSmokeTests/README.md	Updated structure section and test flow description to document the new source generator scenario coverage

test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs

Copilot · 2026-01-02T23:32:20Z

test/AzureFunctionsSmokeTests/run-smoketests.ps1

+                    throw "Unexpected greeting from generated activity: $greeting"
+                }
+
+                if (-not $greetingLength) {


The validation logic checks if greetingLength is falsy before throwing an error. However, zero (0) is a valid length value but evaluates to false in PowerShell. If the greeting were an empty string, the length would be 0, which would incorrectly trigger the error "Greeting length was not populated correctly: 0". Consider checking for null or using -eq $null instead of -not to avoid false positives with zero values.

Suggested change

if (-not $greetingLength) {

if ($null -eq $greetingLength) {

Updated the validation to use null checks so zero-length values are treated correctly. Fix is in commit 8afdd80.

test/AzureFunctionsSmokeTests/run-smoketests.ps1

test/AzureFunctionsSmokeTests/README.md

test/AzureFunctionsSmokeTests/AzureFunctionsSmokeTests.csproj

Co-authored-by: Copilot <[email protected]>

YunchuWang · 2026-01-03T01:12:40Z

@copilot update pr description to follow .github/PULL_REQUEST_TEMPLATE.md

test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs

Co-authored-by: YunchuWang <[email protected]>

Copilot · 2026-01-03T01:15:29Z

@copilot update pr description to follow .github/PULL_REQUEST_TEMPLATE.md

PR description has been refreshed to follow .github/PULL_REQUEST_TEMPLATE.md (see latest PR description update in commit 8afdd80).

YunchuWang · 2026-01-03T01:15:43Z

test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs

EntityInstanceId counterId = new EntityInstanceId(nameof(GeneratorCounter), context.InstanceId);
await context.Entities.SignalEntityAsync(counterId, "Add", length);

@copilot why here use signalentity not callentity?

YunchuWang · 2026-01-03T01:19:38Z

test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs

EntityInstanceId counterId = new EntityInstanceId(nameof(GeneratorCounter), context.InstanceId); await context.Entities.SignalEntityAsync(counterId, "Add", length);

@copilot why here use signalentity not callentity?

@copilot

Co-authored-by: YunchuWang <[email protected]>

Copilot · 2026-01-03T01:19:56Z

[test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs](https://github.com/microsoft/durabletask-dotnet/pull/604/files/a348938284114777ae6bc2102d7bbb9f1736f9a4#diff-83a4409d1c4879a05c11e8765c86929...

Switched to CallEntityAsync so the add operation completes before reading the counter; change is in commit 410895f.

Copilot · 2026-01-03T01:21:50Z

[test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs](https://github.com/microsoft/durabletask-dotnet/pull/604/files/a348938284114777ae6bc2102d7bbb9f1736f9a4#diff-83a4409d1c4879a05c11e8765c869...

Switched to CallEntityAsync so the add operation completes before reading the counter; change is in commit 410895f.

Initial plan

149fe15

Copilot AI assigned Copilot and YunchuWang Jan 2, 2026

Copilot started work on behalf of YunchuWang January 2, 2026 22:32 View session

Copilot AI and others added 2 commits January 2, 2026 22:50

Add source generator smoke test scenario definitions

80e7d37

Co-authored-by: YunchuWang <[email protected]>

Expand Azure Functions smoke tests for source generator coverage

8d9a3a2

Co-authored-by: YunchuWang <[email protected]>

Copilot AI changed the title ~~[WIP] Update smoke test CI for all source generator functionalities~~ Expand Azure Functions smoke tests to cover source generator scenarios Jan 2, 2026

Copilot AI requested a review from YunchuWang January 2, 2026 23:05

Copilot finished work on behalf of YunchuWang January 2, 2026 23:05

YunchuWang marked this pull request as ready for review January 2, 2026 23:27

Copilot AI review requested due to automatic review settings January 2, 2026 23:27

Copilot started reviewing on behalf of YunchuWang January 2, 2026 23:28 View session

Copilot AI reviewed Jan 2, 2026

View reviewed changes

YunchuWang and others added 3 commits January 2, 2026 17:06

Update test/AzureFunctionsSmokeTests/AzureFunctionsSmokeTests.csproj

59594f6

Co-authored-by: Copilot <[email protected]>

Update test/AzureFunctionsSmokeTests/README.md

0158415

Co-authored-by: Copilot <[email protected]>

Update test/AzureFunctionsSmokeTests/run-smoketests.ps1

a348938

Co-authored-by: Copilot <[email protected]>

YunchuWang approved these changes Jan 3, 2026

View reviewed changes

Copilot started work on behalf of YunchuWang January 3, 2026 01:13 View session

YunchuWang reviewed Jan 3, 2026

View reviewed changes

test/AzureFunctionsSmokeTests/SourceGeneratorScenarios.cs Outdated Show resolved Hide resolved

Handle null checks in smoke validation

8afdd80

Co-authored-by: YunchuWang <[email protected]>

Copilot AI requested a review from YunchuWang January 3, 2026 01:16

Copilot finished work on behalf of YunchuWang January 3, 2026 01:16

Copilot started work on behalf of YunchuWang January 3, 2026 01:17 View session

Switch generator entity increment to CallEntityAsync

410895f

Co-authored-by: YunchuWang <[email protected]>

Copilot finished work on behalf of YunchuWang January 3, 2026 01:20

Copilot started work on behalf of YunchuWang January 3, 2026 01:21 View session

Copilot finished work on behalf of YunchuWang January 3, 2026 01:22

YunchuWang added the ready for review label Jan 3, 2026

Merge branch 'main' into copilot/update-smoke-test-ci

d8fde77

kaibocai approved these changes Jan 4, 2026

View reviewed changes

YunchuWang merged commit 546bac4 into main Jan 4, 2026
8 checks passed

YunchuWang deleted the copilot/update-smoke-test-ci branch January 4, 2026 20:17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Expand Azure Functions smoke tests to cover source generator scenarios #604

Expand Azure Functions smoke tests to cover source generator scenarios #604

Copilot AI commented Jan 2, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Copilot AI Jan 2, 2026

Uh oh!

Copilot AI Jan 3, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

YunchuWang commented Jan 3, 2026

Uh oh!

Uh oh!

Copilot AI commented Jan 3, 2026

Uh oh!

YunchuWang commented Jan 3, 2026 •

edited

Loading

Uh oh!

YunchuWang commented Jan 3, 2026

Uh oh!

Copilot AI commented Jan 3, 2026

Uh oh!

Copilot AI commented Jan 3, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Expand Azure Functions smoke tests to cover source generator scenarios #604

Expand Azure Functions smoke tests to cover source generator scenarios #604

Conversation

Copilot AI commented Jan 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What changed?

Why is this change needed?

Issues / work items

Project checklist

AI-assisted code disclosure (required)

Was an AI tool used? (select one)

Testing

Automated tests

Manual validation (only if runtime/behavior changed)

Notes for reviewers

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Copilot AI Jan 2, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 3, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

YunchuWang commented Jan 3, 2026

Uh oh!

Uh oh!

Copilot AI commented Jan 3, 2026

Uh oh!

YunchuWang commented Jan 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

YunchuWang commented Jan 3, 2026

Uh oh!

Copilot AI commented Jan 3, 2026

Uh oh!

Copilot AI commented Jan 3, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Jan 2, 2026 •

edited

Loading

YunchuWang commented Jan 3, 2026 •

edited

Loading